An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello Apple, I am looking for guidance regarding an app that has been waiting for review for an unusually long time. It's the first build and the app details are : App ID: 6771651289 App Title: Authenticator App Status: Waiting for Review Submission Date: March 23, 2026 Submission Type: First App Store Submission My app has remained in the "Waiting for Review" state since March 23, 2026, and I have not yet received any feedback, requests for additional information, or review outcome. I understand that review times can vary depending on workload and review requirements. However, the extended waiting for review period is causing a significant delay to my planned launch, and I would be grateful if the App Review Team could provide an update on the status of the review or advise whether any additional information is needed from my side. Thank you for your time and assistance. I appreciate the work of the App Review Team and look forward to your response. Kind regards, Sufyan

Hello App Review Team, I’m writing this as a last resort after 3 weeks of an exhausting and costly review process for our app Hook — Smart Message Assistant (iOS 1.0.0). Full timeline: • May 3: First submission • June 4: Rejected (marketing language) • June 4: Resubmitted with all fixes • June 8: Rejected (Guideline 3.1.2c — subscriptions) • June 9: Resubmitted with every issue fully addressed June 17: Rejected (Guideline 2.1a — app crash + sign-in bug) • June 17: Resubmitted same day with critical fixes • June 23: Resubmitted again with additional bug fixes • Today: Still “Waiting for Review” — no movement, no communication We have submitted 4 expedited review requests — all approved. We have contacted Developer Support multiple times. Every time we are told “it will begin shortly.” It never does. Business impact: We have a contractual launch deadline and active paid marketing campaigns running. Every week of delay costs us thousands of dollars in direct losses. We have already lost over $10,000 in sunk marketing costs and missed revenue. We have addressed every single issue Apple raised — promptly, thoroughly, and without complaint. We are not asking to skip the process. We are asking for someone to actually look at our submission and tell us if something is blocking it. Apple ID: 6766006483 This is not a normal delay. This is 3-4 weeks of a small team’s work being held hostage with no explanation. Thank you.

Hello, We are seeking guidance regarding our developer account, which is under a Pending Termination Notice under Section 3.2(f). We deeply respect the App Store Review Guidelines and the standards Apple sets to keep the ecosystem safe and trustworthy. We take these rules seriously and submitted an appeal to the App Review Board and, following our correspondence on May 29, provided a full set of additional corrective actions to address the issues identified and bring our products into full compliance — including a mandatory internal compliance process to ensure we meet Apple's standards going forward. It has now been about two weeks, and we have not yet received a response on these latest materials. We have an 8-year history as an Apple Developer Program member, and we want to resolve this properly and rebuild trust. We would be grateful for any guidance from Apple Team or the community on the best way to confirm our materials are under active review, and on any additional steps that would help. Thank you. Reference details: Case ID: 102900026351 Appeal Ticket: APL444296

Hello, My app (Gezo Gündem, a Turkish news app) has been rejected twice under Guideline 4.2.2 (Minimum Functionality), both times with the same generic template: "the app only includes links, images, or content aggregated from the Internet with limited or no native functionality." For the second submission, I provided detailed App Review Notes listing 8 distinct native iOS features with step-by-step testing instructions for each: A native AI summary modal with native favoriting A native theming engine (5 modes) + dynamic "Club Mode" theming via native state management Native offline article storage using the device's file system (fully functional in airplane mode) A native Text-to-Speech engine reading article content aloud Native push notifications when followed authors publish new content A native source/favorites aggregation dashboard A native pinch-to-zoom newspaper cover gallery WebView is used only to render the body text of individual articles — nothing else in the app relies on it. Despite this, the second rejection used the exact same template language, with no reference to any of the listed features. I've since replied via Resolution Center asking the reviewer to re-test following the specific steps in the notes, but I'm unsure if this is the right channel to get a reviewer to actually engage with documented native functionality rather than reissue a template rejection. Has anyone successfully gotten a reviewer to revisit a 4.2.2 rejection by providing this level of detail? Is there a more effective way to ensure the review notes are actually read before a decision is made? Any guidance would be appreciated. Thanks.

Hello, I'm developing a Capacitor/Next.js iOS app with RevenueCat for auto-renewable subscriptions. On a real iPhone via TestFlight, StoreKit never returns my subscription products, so the Apple payment sheet never appears. App TestFlight builds tested: 110, 111, 112 (iOS 1.1.0) In-App Purchase capability enabled on App ID Paid Applications Agreement: active Banking/tax: active Subscription product IDs (auto-renewable, same subscription group) vytalai_premium_monthly vytalai_premium_yearly vytalai_premium_yearly_intro (exit offer) What happens Install app from TestFlight on physical iPhone Navigate to paywall App calls RevenueCat → Purchases.getProducts() with the 3 product IDs above StoreKit returns 0 products (or configure/getProducts times out) UI shows: "Apple Store: 0 subscriptions on this device — Sandbox popup cannot open" Tapping subscribe does not open the Apple payment sheet Fallback prices appear (3.49 / 29.99) instead of live App Store prices (3,49 € / 29,99 €), which suggests StoreKit is not returning products. What we already verified Correct bundle ID in build metadata NEXT_PUBLIC_REVENUECAT_API_KEY_IOS (appl_*) embedded in EAS production build Provisioning profile regenerated and active Subscription metadata corrected (was Rejected, now Waiting for Review) All 3 subscriptions attached to app version submission RevenueCat offering "default" with monthly, annual, and annual_intro packages App Store Server Notifications URL configured to RevenueCat Legal pages open in-app (no external cookie banner on native) Testing on TestFlight only (not Safari/web) App Review context We received Guideline 2.1(b) rejections because: Error on purchase page Exit offer (50% OFF / €1.91 per month equivalent) referenced product vytalai_premium_yearly_intro which was not submitted for review initially — now added and submitted with the app version. Question Even with subscriptions in "Waiting for Review" state and metadata completed, should StoreKit Sandbox/TestFlight return these products on device so we can test the payment sheet before approval? If not, what exact App Store Connect state is required for StoreKit to return products on TestFlight? Any guidance on why getProducts would return 0 for valid product IDs on a TestFlight build would be greatly appreciated. Thank you.

Hello, My app has been in “Waiting for Review” status since May 28. App ID: 1471317275 The app was transferred to my developer account about two months ago. Since the transfer, previous reviews were completed without any issue, and I have not received any message in the Resolution Center or any indication that something is wrong with this submission. I am not sure if the app transfer could have affected the review queue, but the current submission has now been waiting for an unusually long time. Could someone from Apple please advise what I should do in this situation? Should I continue waiting, contact App Review Support directly, or resubmit the build? Thank you for your help.

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

Hi everyone,  I'm a relatively new developer and I just received my first App Store rejection. I'm posting here because I'm genuinely stuck and hoping the community can help me figure out where to even begin.  The Problem:  My app was rejected under Guideline 5.6 - Developer Code of Conduct - Review Suspended. The full message is the standard one: the app doesn't meet the "required quality standard," it's "not eligible for resubmission," and I should "ensure every screen, interaction, and piece of content has been thoughtfully designed" before submitting a new app.  Here's why I'm confused:  The rejection came with ZERO attachments. No screenshots. No screen recordings. No crash logs. No specific mention of a buggy feature, a broken button, or an unfinished screen. It's just a blanket statement about "quality" and "polish."  in my case, there's absolutely nothing to go on.  What I've checked so far:  I've tested the app on multiple physical devices (iPhone 12, 14, 15) – no crashes. I've reviewed every screen for placeholder text, "Lorem Ipsum," or dummy images – none found. I've checked the In-App Purchase / subscription screen for proper legal disclaimers and auto-renewal text – all present. I've made sure there are no debug logs or test toggles left in the production build. Everything looks fine to me, which is why I'm so lost. Without specific feedback, I don't know if the issue is:  A UI inconsistency I'm blind to? A subtle crash that only happens on a device I don't own? An issue with the paywall flow that I've misunderstood? Something about the metadata, screenshots, or app description? My questions for the community:  Has anyone else received a Guideline 5.6 rejection with no attachments? Is this common, or does it suggest the reviewer flagged the app as "low-quality" purely based on first impressions (like the design feels outdated or the concept is too simple)? Since the message says replies and resubmissions of this binary won't be reviewed, and I can't get clarification from the reviewer, what's the safest way to proceed? Should I:  Create a completely new App ID and submit as a new app? Or can I submit a new version under the same App ID? (I've heard mixed answers on this.) More importantly – how do I figure out what to fix? Without a starting point, I'm worried I'll fix the wrong things and get rejected again, which I know can lead to account termination after repeated violations. Are there any "hidden" quality checks that reviewers apply that aren't obvious to developers? For example, does Apple penalize apps that:  Have a generic icon or unpolished splash screen? Take too long to load on first launch? Have unclear navigation or confusing user flow? Lack a proper onboarding/tutorial for first-time users?   Thanks in advance for any help you can offer. I really want to get this right and not waste my one or two remaining chances. my app id : 6764726742

Hi everyone, I'm hoping someone from Apple or a senior community member can help escalate my situation. About four weeks ago, I received a termination warning on my developer account related to an app called Checklist Buddy (originally named Cessna Checklist Buddy). I renamed it after realizing I didn't have formal written permission from Textron Aviation, even though I had verbal approval. I believe that name change — or possibly code similarity between apps — may have triggered a flag. I have three apps on the store: WIB 26, Checklist Buddy, and Pure International 2026. WIB 26 is live and functioning fine. Pure International 2026 is the critical one — it's an event app for a pageant happening next week and delegates are counting on it. I have submitted multiple appeals and tickets over the past four weeks with zero acknowledgment from Apple. Last week I called Apple Support and spoke with a representative. He pulled up my account and confirmed there were notes showing an appeal on file, but no reason whatsoever was documented for the termination warning — even he couldn't see why. He escalated my case to a senior advisor and told me I would hear back within 3 business days. It has now been 7 days with no contact. I understand Apple has a high volume of cases, but this is affecting my livelihood. I have a real event with real attendees next week who need this app, and I cannot distribute it or push updates because my account is in a restricted state pending this appeal. If any Apple staff reads this — my case has been escalated to the senior advisor team and is sitting in an email queue. I just need a resolution or at minimum a reason for the original warning so I can address it properly. Any advice or help from the community is also appreciated. Thank you.

I’m writing this as a last resort after 7 weeks of an exhausting and costly review process for our app Hook — Smart Message Assistant (iOS 1.0.0). Full timeline: • May 3: First submission • June 4: Rejected (marketing language) • June 4: Resubmitted with all fixes • June 8: Rejected (Guideline 3.1.2c — subscriptions) • June 9: Resubmitted with every issue fully addressed • June 17: Rejected (Guideline 2.1a — app crash + sign-in bug) • June 17: Resubmitted same day with critical fixes • June 23: Resubmitted again with additional bug fixes • Today: Still “Waiting for Review” — no movement, no communication We have submitted 4 expedited review requests — all approved. We have contacted Developer Support multiple times. Every time we are told “it will begin shortly.” It never does. Business impact: We have a contractual launch deadline and active paid marketing campaigns running. Every week of delay costs us thousands of dollars in direct losses. We have already lost over $10,000 in sunk marketing costs and missed revenue. We have addressed every single issue Apple raised — promptly, thoroughly, and without complaint. We are not asking to skip the process. We are asking for someone to actually look at our submission and tell us if something is blocking it. Apple ID: 6766006483 This is not a normal delay. This is 4 weeks of a small team’s work being held hostage with no explanation. Thank you.

I submitted an update for my app 7 days ago and it's still sitting in "Waiting for review". This isn't a new app submission—it's an update containing important bug fixes that users are waiting for. I've already contacted Apple Review to ask about the situation and request assistance, but so far I haven't received any update/reply. What makes this even more frustrating is that I've submitted other apps after this one, and those apps were reviewed and approved first. I genuinely don't understand how the review queue works if later submissions can move ahead while an older submission remains untouched. The delay is causing real damage: Users are leaving negative reviews for bugs that have already been fixed in the pending update. Some subscribers have canceled because they assume the issues aren't being addressed. The app's rating and reputation are taking a hit while the fix is effectively locked behind the review process. I'm attaching the email I sent to Apple Review. Has anyone else experienced unusually long review times recently? Have you found any effective way to get visibility into what's causing the delay? I'd be interested to hear whether this is an isolated case or if other developers are seeing the same thing.

Hi everyone, Our app has been in “Waiting for Review” status for 7 days. There are no outstanding actions, messages, or compliance issues shown in App Store Connect. Has anyone experienced similar review delays recently? If so, how long did it take for the review to begin? App ID: 6759098797 Submission ID d6c075db-883c-44fe-8220-005de5a2ed1e Thanks in advance for any guidance.

Hello, I’m writing regarding my app submission, which has remained in “In Review” for over 12 days. I wanted to check whether the review is progressing normally or if there is an issue holding it up. Please let me know if you require any additional information.

Hi guys We have tried to push our app live for over a month now, and there is total radio-silence from apple. Trying to call the Danish/Irish number, no one picks up the phone - we have tried several times and it just keeps playing waiting tone for hours. We have tried writing, but nothing gets back. From may 12th, we got a response on may 28th to update a few things in the app. That was done and then resubmitted. Then again on June 3rd. But from june 3rd, radio silence until june 15th. And now, again radio silence from 15th. We have clients who are waiting for the app, and all of our income relys on this. But no response. I was expecting more from one of the worlds biggest companies.

Hi, Was there an issue or something with the recent App Review queue? Since our app has been in "Waiting for Review" status for about 1 week and got nothing from the review team. App ID: 6759098797 Submission ID: d6c075db-883c-44fe-8220-005de5a2ed1e I'm wondering if we could get any support or help here by posting the issue.

Hello everyone, We have a SaaS product and are currently transitioning our business model. Previously, we used a standard recurring subscription model implemented via StoreKit 2 in our iOS app. Recently, we changed our pricing to a performance-based model, where we charge a percentage fee based on the user's specific usage and performance. On our web platform, we use Stripe to calculate and accept these dynamic percentage-based payments. I have two questions regarding this transition for our iOS app: Payment Gateway: Since our new pricing model is a variable, performance-based percentage rather than a fixed subscription, does Apple allow us to integrate Stripe directly into the iOS app to process these payments? The service provided is digital. Removing Old Subscriptions: We have completely commented out all StoreKit code in our app build since we are no longer offering those plans. However, we cannot find a "Delete" option in App Store Connect to remove the old subscription items. What is the proper way to completely remove these from our app's backend and store listing? Any guidance on the best way to handle this transition and remain compliant with App Review would be greatly appreciated. Thank you!

Hello, my app id 6756081224 Waiting for Review 10 day ago Help me please

Hi everyone, I'm hoping someone from App Review (or anyone who's been through this) can help, because I'm a bit stuck. My app Mingle (Apple ID: 6770285096, Version 1.0.1) has been sitting in "Waiting for Review" for well over a week now. I first submitted at the start of June, and after it sat there for ~6 days with no movement at all, I figured something might be wrong, so I canceled and resubmitted. The new one has now been waiting since June 15 with the same silence: Submission ID: c919ad21-902a-4a3c-a6cc-a5fbd9f7e2b1 Every previous review of this app went through in under 48 hours, so this is really out of the ordinary. I've already opened a support request through Contact Us, but I haven't heard anything back yet. This is genuinely blocking me - I've been trying to get this release out since the beginning of the month and everything on my end is ready and waiting on the review. Is there anything I can do to move this along, or any reason a submission would get stuck like this? If anyone from App Review could take a look, or point me to the right channel, I'd really appreciate it.